Installing the server in silent mode

In silent mode, you specify the installation properties in a text file and then run the server installation without command-line prompts.

About this task

You specify the server installation properties in the install.properties file, which is located in the root folder of the installation files. During the installation process, the server stores these properties in the installed.properties file, which is in the conf/server folder of the server installation files. If you have an already existing installation, you can use its installed.properties file as an example of the properties.
Note: Some of the properties in the table below can be changed after the server has been installed and others cannot. After the server starts for the first time, the server adds other properties to the installed.properties file. Some of these additional properties can be changed and others cannot.

Procedure

  1. Download and extract the installation files for HCL Launch.
    These files are available for download from the HCL FlexNet Operations portal.
  2. If you are using a database other than Apache Derby, place the JAR file for the database in the lib/ext folder of the installation files.
  3. Customize the installation by specifying the properties in the server installation properties file
    If you do not specify a property, the default value is used. These properties are copied to the installed.properties file of the completed installation.

    If you specify a path in a property on a Windows™ system, you must escape any backslash (\) characters that are in the path. For example, to set the install.server.dir property to C:\launch, specify install.server.dir=C\:\\launch. See java.util Class Properties.

    Note: The server.initial.password needs to be specified or install will fail.
    The file looks similar to the following example:
    component.name=HCL Launch 
component.directory=launch/server 
version=7.2.2.0.1130571 
nonInteractive=true 
install.server.dir=/opt/launch/server 
install.java.home=/opt/IBM/ibm-java-i386-80 
install.server.web.always.secure=Y 
install.server.web.host=myserver.example.com 
install.server.web.https.port=8443 
install.server.web.ip=0.0.0.0 
install.server.web.port=8080 
database.type=derby 
hibernate.connection.username=launch 
hibernate.connection.password=password 
hibernate.connection.url=jdbc:derby://host-or-ip:11377/data 
database.derby.port=11377 
license.server.url=27000@RCLServer.example.com 
server.initial.password=admin
  4. Save the file.
  5. Specify the -silent flag when running the installer. Add the flag to the installation file with the command install-server.bat -silent on Windows™ or the command ./install-server.sh -silent on Linux™.

    V7.0 introduces new arguments to the install-server.bat and install-server.sh.

    These scripts behave identically and take combinations of the following arguments: 
    -silent -install-dir /path/to/install -java /path/to/jdk
    They each correspond to properties in install.properties , and if specified they will override them. Corresponding properties are as follows:
    Table 1.
    Argument Property Note
    -silent nonInteractive=true Running with -silent and without an -install-dir results in an error.
    -install-dir /path/to/dir install.server.dir=/path/to/dir Setting an install-dir that already has server results in a server upgrade.
    -java /path/to/jdk install.java.home=/path/to/jdk Running with -java for a server upgrade results in an error.

Results

The installation program installs the server. The properties that are set during installation are recorded in the file server_install/conf/server/installed.properties on the server.

If you install the server as a node in high-availability cluster, the installer loads the existing encryption keystore that is in the shared storage folder by using the default settings. If the default password is incorrect, you are prompted for the password. If after three attempts you do not enter the correct password, the installation process stops. If the keystore has more than one alias, you are prompted to specify an alias.

What to do next

To start the server, see Starting and stopping the server.
When you run the server for the first time, you might see an error message that says that no agent or tag is configured to import new component versions. To import component versions, including built artifacts, you must use an agent, and the server requires that you specify a default agent for this purpose. You can override this default setting when you create a component. Follow these steps to specify a default agent or agent tag:
  • To specify a default agent, click System > System Settings and under General Settings, clear the Use Agent Tag For Integration check box. Then, select an agent in the Agent for Version Imports list. Then, at the bottom of the page, click Save.
  • To specify a default agent tag, click Settings > System Settings and under General Settings, clear the Use Agent Tag For Integration check box. Then, select an agent tag in the Agent Tag for version imports list. Then, at the bottom of the page, click Save. If no tags are listed, add a tag to one or more agents on the server.

If you see "Out of memory" errors, increase the amount of memory that is available to the HCL Launch service. See Increasing the amount of memory that is available to the server.

If you are using Derby, you might see the following error in the results of the installation program:
[echo] waiting for db to start - 6 seconds remaining
[echo] waiting for db to start - 3 seconds remaining
[echo] Could not start database
[echo] Stopping embedded database ...
[java] Tue Feb 04 09:11:25 EST 2014 : Could not connect 
  to Derby Network Server on host localhost, port 11377: 
  Connection refused
If you see this error, you must change the default security settings for the Java™ installation on the server:
  1. Open the Java™ security policy file in a text editor. If you are using a Java™ Runtime Environment (JRE), this file is at the location JAVA_HOME/lib/security/java.policy, where JAVA_HOME is the base folder of the Java™ installation. If you are using a Java™ Development Kit (JDK), the file is at the location JAVA_HOME/jre/lib/security/java.policy.
  2. In the java.policy file, in the section that is labeled // default permissions granted to all domains, within the grant{} block, add the following code:
    permission java.net.SocketPermission "localhost:11377", "listen";
  3. Run the installation program again.